The Sessions Limit controls the active number of browser sessions allowed to connect simultaneously to a single ASP.NET application.

How is the Sessions Limit Enforced?

When the license is validated DeployLX determines if the thread represents an ASP.NET request.

• For ASP.NET requests, DeployLX will track each user session. When the total allowed has been reached validation fails.
• If the thread does not represent an ASP.NET request validation continues normally.
• If the thread is for an ASP.NET request and sessions are disabled or the ASP.NET session timeout is less than the configured timeout then validation fails.

Counting Sessions

Each time the license is validated DeployLX checks the list of current sessions. If a session has not been used within the configured timeout period it is released from use and can be assigned to a new user.

When a new browser window is opened by the same user on their machine the same session id will be used. However if the user starts an entirely new browser, by selecting the browser icon from their start menu, a new session will be assigned to that browser. This can result in a single user holding more than one active session on the server.

See Also